Context-sensitive remote eyewear controller

ABSTRACT

Context-sensitive remote controls for use with electronic devices (e.g., eyewear device). The electronic device is configured to perform activities (e.g., email, painting, navigation, gaming). The context-sensitive remote control includes a display having a display area, a display driver coupled to the display, and a transceiver. The remote control additionally includes memory that stores controller layout configurations for display in the display area of the display by the display driver. A processor in the context-sensitive remote control is configured to establish, via the transceiver, communication with an electronic device, detect an activity currently being performed by the electronic device, select one of the controller layout configurations responsive to the detected activity, and present, via the display driver, the selected controller layout configuration in the display area of the display.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No.17/034,700 filed on Sep. 28, 2020, the contents of which areincorporated fully herein by reference.

TECHNICAL FIELD

This disclosure relates to a remote control for eyewear. Morespecifically, this disclosure relates to a configurable remote controlthat adapts to activity taking place on the eyewear (i.e., acontext-sensitive remote control).

BACKGROUND

Many types of mobile electronic devices available today, such assmartphones, tablets, laptops, handheld devices, and wearable devices(e.g., smart glasses, digital eyewear, headwear, headgear, andhead-mounted displays), include a variety of cameras, sensors, wirelesstransceivers, input systems (e.g., touch-sensitive surfaces, pointers),peripheral devices, displays, and graphical user interfaces (GUIs)through which a user can interact with displayed content.

Remote controls enable users to interact with electronic devices. Theremote controls may be connected to the electronic devices via a wiredor a wireless connection.

BRIEF DESCRIPTION OF THE DRAWINGS

Features of the various examples described will be readily understoodfrom the following detailed description, in which reference is made tothe figures. A reference numeral is used with each element in thedescription and throughout the several views of the drawing. When aplurality of similar elements is present, a single reference numeral maybe assigned to like elements, with an added lower-case letter referringto a specific element. When referring to such elements collectively orto one or more non-specific elements, the lower-case letter may beomitted.

The various elements shown in the figures are not drawn to scale unlessotherwise indicated. The dimensions of the various elements may beenlarged or reduced in the interest of clarity. The several figuresdepict one or more implementations that are presented by way of exampleonly and should not be construed as limiting. Included in the drawingare the following figures:

FIG. 1A is a side view (right) of an example hardware configuration ofan eyewear device suitable for use in a context-sensitive remote controlsystem;

FIG. 1B is a perspective, partly sectional view of a right corner of theeyewear device of FIG. 1A depicting a right visible-light camera, and acircuit board;

FIG. 1C is a side view (left) of an example hardware configuration ofthe eyewear device of FIG. 1A, which shows a left visible-light camera;

FIG. 1D is a perspective, partly sectional view of a left corner of theeyewear device of FIG. 1C depicting the left visible-light camera, and acircuit board;

FIGS. 2A and 2B are rear views of example hardware configurations ofeyewear devices with displays;

FIG. 3 is a diagrammatic depiction of a three-dimensional scene, a leftraw image captured by a left visible-light camera, and a right raw imagecaptured by a right visible-light camera;

FIG. 4 is a functional block diagram of an example context-sensitiveremote control system including a wearable device (e.g., an eyeweardevice), a mobile device (e.g., acting as a context-sensitive remotecontrol) and a server system connected via various networks;

FIG. 5 is a diagrammatic representation of an example hardwareconfiguration for a mobile device of the context-sensitive remotecontrol system of FIG. 4 ;

FIG. 6 is a schematic illustration of an eyewear device,context-sensitive remote control, and a network device;

FIG. 7A is an illustration of a context-sensitive remote control with acontroller layout configuration;

FIGS. 7B, 7C, and 7D are illustrations of controller layout componentsfor use in configuring the context-sensitive remote control;

FIGS. 8A and 8B are illustrations of a context-sensitive remote controlwith a touchpad layout configuration in a vertical orientation and ahorizontal orientation, respectively;

FIGS. 9A and 9B are illustrations of a context-sensitive remote controlwith a keyboard layout configuration in a vertical orientation and ahorizontal orientation, respectively; and

FIGS. 10A, 10B, 10C, 10D, 10E, 10F, and 10G are flow charts includingsteps for implementing a context-sensitive remote control.

DETAILED DESCRIPTION

Various implementations and details are described with reference toexamples including a context-sensitive remote control system for anelectronic device (such as an eyewear device). A context-sensitiveremote control adapts to activity of the electronic device. For example,if the electronic device is in use to compose an email message, akeyboard is present on the context-sensitive remote control; if theelectronic device is in use to play a game, a game controller is presenton the context-sensitive remote control; if the electronic device isdisplaying a user interface (e.g., a GUI), a navigation screencorresponding to the user interface is present on the context-sensitiveremote control; and if the electronic device is in use to paint apicture, a touch pad is present on the context-sensitive remote control.

The following detailed description includes systems, methods,techniques, instruction sequences, and computing machine programproducts illustrative of examples set forth in the disclosure. Numerousdetails and examples are included for the purpose of providing athorough understanding of the disclosed subject matter and its relevantteachings. Those skilled in the relevant art, however, may understandhow to apply the relevant teachings without such details. Aspects of thedisclosed subject matter are not limited to the specific devices,systems, and method described because the relevant teachings can beapplied or practice in a variety of ways. The terminology andnomenclature used herein is for the purpose of describing particularaspects only and is not intended to be limiting. In general, well-knowninstruction instances, protocols, structures, and techniques are notnecessarily shown in detail.

The terms “coupled” or “connected” as used herein refer to any logical,optical, physical, or electrical connection, including a link or thelike by which the electrical or magnetic signals produced or supplied byone system element are imparted to another coupled or connected systemelement. Unless described otherwise, coupled or connected elements ordevices are not necessarily directly connected to one another and may beseparated by intermediate components, elements, or communication media,one or more of which may modify, manipulate, or carry the electricalsignals. The term “on” means directly supported by an element orindirectly supported by the element through another element that isintegrated into or supported by the element.

The term “proximal” is used to describe an item or part of an item thatis situated near, adjacent, or next to an object or person; or that iscloser relative to other parts of the item, which may be described as“distal.” For example, the end of an item nearest an object may bereferred to as the proximal end, whereas the generally opposing end maybe referred to as the distal end.

The orientations of the eyewear device, other mobile devices (such ascontext-sensitive remote controls), associated components and any otherdevices incorporating, for example, a camera, an inertial measurementunit, or both such as shown in any of the drawings, are given by way ofexample only, for illustration and discussion purposes. In operation,the eyewear device may be oriented in any other direction suitable tothe particular application of the eyewear device; for example, up, down,sideways, or any other orientation. Also, to the extent used herein, anydirectional term, such as front, rear, inward, outward, toward, left,right, lateral, longitudinal, up, down, upper, lower, top, bottom, side,horizontal, vertical, and diagonal are used by way of example only, andare not limiting as to the direction or orientation of any camera orinertial measurement unit as constructed or as otherwise describedherein.

Additional objects, advantages and novel features of the examples willbe set forth in part in the following description, and in part willbecome apparent to those skilled in the art upon examination of thefollowing and the accompanying drawings or may be learned by productionor operation of the examples. The objects and advantages of the presentsubject matter may be realized and attained by means of themethodologies, instrumentalities and combinations particularly pointedout in the appended claims.

Reference now is made in detail to the examples illustrated in theaccompanying drawings and discussed below.

FIG. 1A is a side view (right) of an example hardware configuration ofan eyewear device 100 which includes a touch-sensitive input device ortouchpad 181. As shown, the touchpad 181 may have a boundary that issubtle and not easily seen; alternatively, the boundary may be plainlyvisible or include a raised or otherwise tactile edge that providesfeedback to the user about the location and boundary of the touchpad181. In other implementations, the eyewear device 100 may additionallyor alternatively include a touchpad on the left side.

The surface of the touchpad 181 is configured to detect finger touches,taps, and gestures (e.g., moving touches) for use with a graphical userinterface (GUI) displayed by the eyewear device, on an image display, toallow the user to navigate through and select menu options in anintuitive manner, which enhances and simplifies the user experience.

Detection of finger inputs on the touchpad 181 can enable severalfunctions. For example, touching anywhere on the touchpad 181 may causethe GUI to display or highlight an item on the image display, which maybe projected onto at least one of the optical assemblies 180A, 180B.Double tapping on the touchpad 181 may select an item or icon. Slidingor swiping a finger in a particular direction (e.g., from front to back,back to front, up to down, or down to) may cause the items or icons toslide or scroll in a particular direction; for example, to move to anext item, icon, video, image, page, or slide. Sliding the finger inanother direction may slide or scroll in the opposite direction; forexample, to move to a previous item, icon, video, image, page, or slide.The touchpad 181 can be virtually anywhere on the eyewear device 100.

In one example, an identified finger gesture of a single tap on thetouchpad 181, initiates selection or pressing of a graphical userinterface element in the image presented on the image display of theoptical assembly 180A, 180B. An adjustment to the image presented on theimage display of the optical assembly 180A, 180B based on the identifiedfinger gesture can be a primary action which selects or submits thegraphical user interface element on the image display of the opticalassembly 180A, 180B for further display or execution.

As shown, the eyewear device 100 includes a right visible-light camera114B. As further described herein, two cameras 114A, 114B capture imageinformation for a scene from two separate viewpoints. The two capturedimages may be used to project a three-dimensional display onto an imagedisplay for viewing with 3D glasses.

The eyewear device 100 includes a right optical assembly 180B with animage display to present images, such as depth images. As shown in FIGS.1A and 1B, the eyewear device 100 includes the right visible-lightcamera 114B. The eyewear device 100 can include multiple visible-lightcameras 114A, 114B that form a passive type of three-dimensional camera,such as stereo camera, of which the right visible-light camera 114B islocated on a right corner 110B. As shown in FIGS. 1C-D, the eyeweardevice 100 also includes a left visible-light camera 114A.

Left and right visible-light cameras 114A, 114B are sensitive to thevisible-light range wavelength. Each of the visible-light cameras 114A,114B have a different frontward facing field of view which areoverlapping to enable generation of three-dimensional depth images, forexample, right visible-light camera 114B depicts a right field of view111B. Generally, a “field of view” is the part of the scene that isvisible through the camera at a particular position and orientation inspace. The fields of view 111A and 111B have an overlapping field ofview 304 (FIG. 3 ). Objects or object features outside the field of view111A, 111B when the visible-light camera captures the image are notrecorded in a raw image (e.g., photograph or picture). The field of viewdescribes an angle range or extent, which the image sensor of thevisible-light camera 114A, 114B picks up electromagnetic radiation of agiven scene in a captured image of the given scene. Field of view can beexpressed as the angular size of the view cone; i.e., an angle of view.The angle of view can be measured horizontally, vertically, ordiagonally.

In an example, visible-light cameras 114A, 114B have a field of viewwith an angle of view between 15° to 110°, for example 24°, and have aresolution of 480×480 pixels (or greater). The “angle of coverage”describes the angle range that a lens of visible-light cameras 114A,114B or infrared camera 410 (see FIG. 2A) can effectively image.Typically, the camera lens produces an image circle that is large enoughto cover the film or sensor of the camera completely, possibly includingsome vignetting (e.g., a darkening of the image toward the edges whencompared to the center). If the angle of coverage of the camera lensdoes not fill the sensor, the image circle will be visible, typicallywith strong vignetting toward the edge, and the effective angle of viewwill be limited to the angle of coverage.

Examples of such visible-light cameras 114A, 114B include ahigh-resolution complementary metal-oxide-semiconductor (CMOS) imagesensor and a digital VGA camera (video graphics array) capable ofresolutions of 640p (e.g., 640×480 pixels for a total of 0.3megapixels), 720p, 1080p (or greater). Other examples of visible-lightcameras 114A, 114B that can capture high-definition (HD) still imagesand store them at a resolution of 1642 by 1642 pixels (or greater); orrecord high-definition video at a high frame rate (e.g., thirty to sixtyframes per second or more) and store the recording at a resolution of1216 by 1216 pixels (or greater).

The eyewear device 100 may capture image sensor data from thevisible-light cameras 114A, 114B along with geolocation data, digitizedby an image processor, for storage in a memory. The visible-lightcameras 114A, 114B capture respective left and right raw images in thetwo-dimensional space domain that comprise a matrix of pixels on atwo-dimensional coordinate system that includes an X-axis for horizontalposition and a Y-axis for vertical position. Each pixel includes a colorattribute value (e.g., a red pixel light value, a green pixel lightvalue, or a blue pixel light value); and a position attribute (e.g., anX-axis coordinate and a Y-axis coordinate).

In order to capture stereo images for later display as athree-dimensional projection, the image processor 412 (shown in FIG. 4 )may be coupled to the visible-light cameras 114A, 114B to receive andstore the visual image information. The image processor 412, or anotherprocessor, controls operation of the visible-light cameras 114A, 114B toact as a stereo camera simulating human binocular vision and may add atimestamp to each image. The timestamp on each pair of images allowsdisplay of the images together as part of a three-dimensionalprojection. Three-dimensional projections produce an immersive,life-like experience that is desirable in a variety of contexts,including virtual reality (VR) and video gaming.

FIG. 1B is a perspective, cross-sectional view of a right corner 110B ofthe eyewear device 100 of FIG. 1A depicting the right visible-lightcamera 114B of the camera system, and a circuit board. FIG. 1C is a sideview (left) of an example hardware configuration of an eyewear device100 of FIG. 1A, which shows a left visible-light camera 114A of thecamera system. FIG. 1D is a perspective, cross-sectional view of a leftcorner 110A of the eyewear device of FIG. 1C depicting the leftvisible-light camera 114A of the three-dimensional camera, and a circuitboard.

Construction and placement of the left visible-light camera 114A issubstantially similar to the right visible-light camera 114B, except theconnections and coupling are on the left lateral side 170A. As shown inthe example of FIG. 1B, the eyewear device 100 includes the rightvisible-light camera 114B and a circuit board 140B, which may be aflexible printed circuit board (PCB). The right hinge 126B connects theright corner 110B to a right temple 125B of the eyewear device 100. Insome examples, components of the right visible-light camera 114B, theflexible PCB 140B, or other electrical connectors or contacts may belocated on the right temple 125B or the right hinge 126B.

The right corner 110B includes corner body 190 and a corner cap, withthe corner cap omitted in the cross-section of FIG. 1B. Disposed insidethe right corner 110B are various interconnected circuit boards, such asPCBs or flexible PCBs, that include controller circuits for rightvisible-light camera 114B, microphone(s), low-power wireless circuitry(e.g., for wireless short range network communication via Bluetooth™),high-speed wireless circuitry (e.g., for wireless local area networkcommunication via Wi-Fi).

The right visible-light camera 114B is coupled to or disposed on theflexible PCB 140B and covered by a visible-light camera cover lens,which is aimed through opening(s) formed in the frame 105. For example,the right rim 107B of the frame 105, shown in FIG. 2A, is connected tothe right corner 110B and includes the opening(s) for the visible-lightcamera cover lens. The frame 105 includes a front side configured toface outward and away from the eye of the user. The opening for thevisible-light camera cover lens is formed on and through the front oroutward-facing side of the frame 105. In the example, the rightvisible-light camera 114B has an outward-facing field of view 111B(shown in FIG. 3 ) with a line of sight or perspective that iscorrelated with the right eye of the user of the eyewear device 100. Thevisible-light camera cover lens can also be adhered to a front side oroutward-facing surface of the right corner 110B in which an opening isformed with an outward-facing angle of coverage, but in a differentoutwardly direction. The coupling can also be indirect via interveningcomponents.

As shown in FIG. 1B, flexible PCB 140B is disposed inside the rightcorner 110B and is coupled to one or more other components housed in theright corner 110B. Although shown as being formed on the circuit boardsof the right corner 110B, the right visible-light camera 114B can beformed on the circuit boards of the left corner 110A, the temples 125A,125B, or the frame 105.

FIGS. 2A and 2B are perspective views, from the rear, of examplehardware configurations of the eyewear device 100, including twodifferent types of image displays. The eyewear device 100 is sized andshaped in a form configured for wearing by a user; the form ofeyeglasses is shown in the example. The eyewear device 100 can takeother forms and may incorporate other types of frameworks; for example,a headgear, a headset, or a helmet.

In the eyeglasses example, eyewear device 100 includes a frame 105including a left rim 107A connected to a right rim 107B via a bridge 106adapted to be supported by a nose of the user. The left and right rims107A, 107B include respective apertures 175A, 175B, which hold arespective optical element 180A, 180B, such as a lens and a displaydevice. As used herein, the term “lens” is meant to include transparentor translucent pieces of glass or plastic having curved or flat surfacesthat cause light to converge/diverge or that cause little or noconvergence or divergence.

Although shown as having two optical elements 180A, 180B, the eyeweardevice 100 can include other arrangements, such as a single opticalelement (or it may not include any optical element 180A, 180B),depending on the application or the intended user of the eyewear device100. As further shown, eyewear device 100 includes a left corner 110Aadjacent the left lateral side 170A of the frame 105 and a right corner110B adjacent the right lateral side 170B of the frame 105. The corners110A, 110B may be integrated into the frame 105 on the respective sides170A, 170B (as illustrated) or implemented as separate componentsattached to the frame 105 on the respective sides 170A, 170B.Alternatively, the corners 110A, 110B may be integrated into temples(not shown) attached to the frame 105.

In one example, the image display of optical assembly 180A, 180Bincludes an integrated image display. As shown in FIG. 2A, each opticalassembly 180A, 180B includes a suitable display matrix 177, such as aliquid crystal display (LCD), an organic light-emitting diode (OLED)display, or any other such display. Each optical assembly 180A, 180Balso includes an optical layer or layers 176, which can include lenses,optical coatings, prisms, mirrors, waveguides, optical strips, and otheroptical components in any combination. The optical layers 176A, 176B, .. . 176N (shown as 176A-N in FIG. 2A and herein) can include a prismhaving a suitable size and configuration and including a first surfacefor receiving light from a display matrix and a second surface foremitting light to the eye of the user. The prism of the optical layers176A-N extends over all or at least a portion of the respectiveapertures 175A, 175B formed in the left and right rims 107A, 107B topermit the user to see the second surface of the prism when the eye ofthe user is viewing through the corresponding left and right rims 107A,107B. The first surface of the prism of the optical layers 176A-N facesupwardly from the frame 105 and the display matrix 177 overlies theprism so that photons and light emitted by the display matrix 177impinge the first surface. The prism is sized and shaped so that thelight is refracted within the prism and is directed toward the eye ofthe user by the second surface of the prism of the optical layers176A-N. In this regard, the second surface of the prism of the opticallayers 176A-N can be convex to direct the light toward the center of theeye. The prism can optionally be sized and shaped to magnify the imageprojected by the display matrix 177, and the light travels through theprism so that the image viewed from the second surface is larger in oneor more dimensions than the image emitted from the display matrix 177.

In one example, the optical layers 176A-N may include an LCD layer thatis transparent (keeping the lens open) unless and until a voltage isapplied which makes the layer opaque (closing or blocking the lens). Theimage processor 412 on the eyewear device 100 may execute programming toapply the voltage to the LCD layer in order to produce an active shuttersystem, making the eyewear device 100 suitable for viewing visualcontent when displayed as a three-dimensional projection. Technologiesother than LCD may be used for the active shutter mode, including othertypes of reactive layers that are responsive to a voltage or anothertype of input.

In another example, the image display device of optical assembly 180A,180B includes a projection image display as shown in FIG. 2B. Eachoptical assembly 180A, 180B includes a laser projector 150, which is athree-color laser projector using a scanning mirror or galvanometer.During operation, an optical source such as a laser projector 150 isdisposed in or on one of the temples 125A, 125B of the eyewear device100. Optical assembly 180B in this example includes one or more opticalstrips 155A, 155B, . . . 155N (shown as 155A-N in FIG. 2B) which arespaced apart and across the width of the lens of each optical assembly180A, 180B or across a depth of the lens between the front surface andthe rear surface of the lens.

As the photons projected by the laser projector 150 travel across thelens of each optical assembly 180A, 180B, the photons encounter theoptical strips 155A-N. When a particular photon encounters a particularoptical strip, the photon is either redirected toward the user's eye, orit passes to the next optical strip. A combination of modulation oflaser projector 150, and modulation of optical strips, may controlspecific photons or beams of light. In an example, a processor controlsoptical strips 155A-N by initiating mechanical, acoustic, orelectromagnetic signals. Although shown as having two optical assemblies180A, 180B, the eyewear device 100 can include other arrangements, suchas a single or three optical assemblies, or each optical assembly 180A,180B may have arranged different arrangement depending on theapplication or intended user of the eyewear device 100.

As further shown in FIGS. 2A and 2B, eyewear device 100 includes a leftcorner 110A adjacent the left lateral side 170A of the frame 105 and aright corner 110B adjacent the right lateral side 170B of the frame 105.The corners 110A, 110B may be integrated into the frame 105 on therespective lateral sides 170A, 170B (as illustrated) or implemented asseparate components attached to the frame 105 on the respective sides170A, 170B. Alternatively, the corners 110A, 110B may be integrated intotemples 125A, 125B attached to the frame 105.

In another example, the eyewear device 100 shown in FIG. 2B may includetwo projectors, a left projector 150A (not shown) and a right projector150B (shown as projector 150). The left optical assembly 180A mayinclude a left display matrix 177A (not shown) or a left set of opticalstrips 155′A, 155′B, . . . 155′N (155 prime, A through N, not shown)which are configured to interact with light from the left projector150A. Similarly, the right optical assembly 180B may include a rightdisplay matrix 177B (not shown) or a right set of optical strips 155″A,155″B, . . . 155″N (155 double prime, A through N, not shown) which areconfigured to interact with light from the right projector 150B. In thisexample, the eyewear device 100 includes a left display and a rightdisplay.

FIG. 3 is a diagrammatic depiction of a three-dimensional scene 306, aleft raw image 302A captured by a left visible-light camera 114A, and aright raw image 302B captured by a right visible-light camera 114B. Theleft field of view 111A may overlap, as shown, with the right field ofview 111B. The overlapping field of view 304 represents that portion ofthe image captured by both cameras 114A, 114B. The term ‘overlapping’when referring to field of view means the matrix of pixels in thegenerated raw images overlap by thirty percent (30%) or more.‘Substantially overlapping’ means the matrix of pixels in the generatedraw images—or in the infrared image of scene—overlap by fifty percent(50%) or more. As described herein, the two raw images 302A, 302B may beprocessed to include a timestamp, which allows the images to bedisplayed together as part of a three-dimensional projection.

For the capture of stereo images, as illustrated in FIG. 3 , a pair ofraw red, green, and blue (RGB) images are captured of a real scene 306at a given moment in time—a left raw image 302A captured by the leftcamera 114A and right raw image 302B captured by the right camera 114B.When the pair of raw images 302A, 302B are processed (e.g., by the imageprocessor 412), depth images are generated. The generated depth imagesmay be viewed on an optical assembly 180A, 180B of an eyewear device, onanother display (e.g., the image display 580 on a mobile device 401), oron a screen.

The generated depth images are in the three-dimensional space domain andcan comprise a matrix of vertices on a three-dimensional locationcoordinate system that includes an X axis for horizontal position (e.g.,length), a Y axis for vertical position (e.g., height), and a Z axis fordepth (e.g., distance). Each vertex may include a color attribute (e.g.,a red pixel light value, a green pixel light value, or a blue pixellight value); a position attribute (e.g., an X location coordinate, a Ylocation coordinate, and a Z location coordinate); a texture attribute;a reflectance attribute; or a combination thereof. The texture attributequantifies the perceived texture of the depth image, such as the spatialarrangement of color or intensities in a region of vertices of the depthimage.

In one example, the context-sensitive remote control system 400 (FIG. 4) includes the eyewear device 100, which includes a frame 105 and a leftcorner 110A extending from a left lateral side 170A of the frame 105 anda right temple 125B extending from a right lateral side 170B of theframe 105. The eyewear device 100 may further include at least twovisible-light cameras 114A, 114B having overlapping fields of view. Inone example, the eyewear device 100 includes a left visible-light camera114A with a left field of view 111A, as illustrated in FIG. 3 . The leftcamera 114A is connected to the frame 105 or the left corner 110A tocapture a left raw image 302A from the left side of scene 306. Theeyewear device 100 further includes a right visible-light camera 114Bwith a right field of view 111B. The right camera 114B is connected tothe frame 105 or the right temple 125B to capture a right raw image 302Bfrom the right side of scene 306.

FIG. 4 is a functional block diagram of an example context-sensitiveremote control system 400 that includes a wearable device (e.g., aneyewear device 100), a mobile device 401, and a server system 498connected via various networks 495 such as the Internet. Thecontext-sensitive remote control system 400 includes a low-powerwireless connection 425 and a high-speed wireless connection 437 betweenthe eyewear device 100 and the mobile device 401.

As shown in FIG. 4 , the eyewear device 100 includes one or morevisible-light cameras 114A, 114B that capture still images, videoimages, or both still and video images, as described herein. The cameras114A, 114B may have a direct memory access (DMA) to high-speed circuitry430 and function as a stereo camera. The cameras 114A, 114B may be usedto capture initial-depth images that may be rendered intothree-dimensional (3D) models that are texture-mapped images of a red,green, and blue (RGB) imaged scene. The device 100 may also include adepth sensor 213, which uses infrared signals to estimate the positionof objects relative to the device 100. The depth sensor 213 in someexamples includes one or more infrared emitter(s) 215 and infraredcamera(s) 410.

The eyewear device 100 further includes two image displays of eachoptical assembly 180A, 180B (one associated with the left side 170A andone associated with the right side 170B). The eyewear device 100 alsoincludes an image display driver 442, an image processor 412, low-powercircuitry 420, and high-speed circuitry 430. The image displays of eachoptical assembly 180A, 180B are for presenting images, including stillimages, video images, or still and video images. The image displaydriver 442 is coupled to the image displays of each optical assembly180A, 180B in order to control the display of images.

The eyewear device 100 additionally includes one or more speakers 440(e.g., one associated with the left side of the eyewear device andanother associated with the right side of the eyewear device). Thespeakers 440 may be incorporated into the frame 105, temples 125, orcorners 110 of the eyewear device 100. The one or more speakers 440 aredriven by audio processor 443 under control of low-power circuitry 420,high-speed circuitry 430, or both. The speakers 440 are for presentingaudio signals including, for example, a beat track. The audio processor443 is coupled to the speakers 440 in order to control the presentationof sound.

The components shown in FIG. 4 for the eyewear device 100 are located onone or more circuit boards, for example a printed circuit board (PCB) orflexible printed circuit (FPC), located in the rims or temples.Alternatively, or additionally, the depicted components can be locatedin the corners, frames, hinges, or bridge of the eyewear device 100.Left and right visible-light cameras 114A, 114B can include digitalcamera elements such as a complementary metal-oxide-semiconductor (CMOS)image sensor, a charge-coupled device, a lens, or any other respectivevisible or light capturing elements that may be used to capture data,including still images or video of scenes with unknown objects.

As shown in FIG. 4 , high-speed circuitry 430 includes a high-speedprocessor 432, a memory 434, and high-speed wireless circuitry 436. Inthe example, the image display driver 442 is coupled to the high-speedcircuitry 430 and operated by the high-speed processor 432 in order todrive the left and right image displays of each optical assembly 180A,180B. High-speed processor 432 may be any processor capable of managinghigh-speed communications and operation of any general computing systemneeded for eyewear device 100. High-speed processor 432 includesprocessing resources needed for managing high-speed data transfers onhigh-speed wireless connection 437 to a wireless local area network(WLAN) using high-speed wireless circuitry 436.

In some examples, the high-speed processor 432 executes an operatingsystem such as a LINUX operating system or other such operating systemof the eyewear device 100 and the operating system is stored in memory434 for execution. In addition to any other responsibilities, thehigh-speed processor 432 executes a software architecture for theeyewear device 100 that is used to manage data transfers with high-speedwireless circuitry 436. In some examples, high-speed wireless circuitry436 is configured to implement Institute of Electrical and ElectronicEngineers (IEEE) 802.11 communication standards, also referred to hereinas Wi-Fi. In other examples, other high-speed communications standardsmay be implemented by high-speed wireless circuitry 436.

The low-power circuitry 420 includes a low-power processor 422 andlow-power wireless circuitry 424. The low-power wireless circuitry 424and the high-speed wireless circuitry 436 of the eyewear device 100 caninclude short-range transceivers (Bluetooth™ or Bluetooth Low-Energy(BLE)) and wireless wide, local, or wide-area network transceivers(e.g., cellular or Wi-Fi). Mobile device 401, including the transceiverscommunicating via the low-power wireless connection 425 and thehigh-speed wireless connection 437, may be implemented using details ofthe architecture of the eyewear device 100, as can other elements of thenetwork 495.

Memory 434 includes any storage device capable of storing various dataand applications, including, among other things, camera data generatedby the left and right visible-light cameras 114A, 114B, the infraredcamera(s) 410, the image processor 412, and images generated for displayby the image display driver 442 on the image display of each opticalassembly 180A, 180B. Although the memory 434 is shown as integrated withhigh-speed circuitry 430, the memory 434 in other examples may be anindependent, standalone element of the eyewear device 100. In certainsuch examples, electrical routing lines may provide a connection througha chip that includes the high-speed processor 432 from the imageprocessor 412 or low-power processor 422 to the memory 434. In otherexamples, the high-speed processor 432 may manage addressing of memory434 such that the low-power processor 422 will boot the high-speedprocessor 432 any time that a read or write operation involving memory434 is needed.

As shown in FIG. 4 , the high-speed processor 432 of the eyewear device100 can be coupled to the camera system (visible-light cameras 114A,114B), the image display driver 442, the user input device 491, and thememory 434. As shown in FIG. 5 , the CPU 530 of the mobile device 401may be coupled to a camera system 570, an image display driver 582, auser input layer 591, and a memory 540A.

The server system 498 may be one or more computing devices as part of aservice or network computing system, for example, that include aprocessor, a memory, and network communication interface to communicateover the network 495 with an eyewear device 100 and a mobile device 401.

The output components of the eyewear device 100 include visual elements,such as the left and right image displays associated with each lens oroptical assembly 180A, 180B as described in FIGS. 2A and 2B (e.g., adisplay such as a liquid crystal display (LCD), a plasma display panel(PDP), a light emitting diode (LED) display, a projector, or awaveguide). The eyewear device 100 may include a user-facing indicator(e.g., an LED, a loudspeaker, or a vibrating actuator), or anoutward-facing signal (e.g., an LED, a loudspeaker). The image displaysof each optical assembly 180A, 180B are driven by the image displaydriver 442. In some example configurations, the output components of theeyewear device 100 further include additional indicators such as audibleelements (e.g., loudspeakers), tactile components (e.g., an actuatorsuch as a vibratory motor to generate haptic feedback), and other signalgenerators. For example, the device 100 may include a user-facing set ofindicators, and an outward-facing set of signals. The user-facing set ofindicators are configured to be seen or otherwise sensed by the user ofthe device 100. For example, the device 100 may include an LED displaypositioned so the user can see it, a one or more speakers positioned togenerate a sound the user can hear, or an actuator to provide hapticfeedback the user can feel. The outward-facing set of signals areconfigured to be seen or otherwise sensed by an observer near the device100. Similarly, the device 100 may include an LED, a loudspeaker, or anactuator that is configured and positioned to be sensed by an observer.

The input components of the eyewear device 100 may include alphanumericinput components (e.g., a touch screen or touchpad configured to receivealphanumeric input, a photo-optical keyboard, or otheralphanumeric-configured elements), pointer-based input components (e.g.,a mouse, a touchpad, a trackball, a joystick, a motion sensor, or otherpointing instruments), tactile input components (e.g., a button switch,a touch screen or touchpad that senses the location, force or locationand force of touches or touch gestures, or other tactile-configuredelements), and audio input components (e.g., a microphone), and thelike. The mobile device 401 and the server system 498 may includealphanumeric, pointer-based, tactile, audio, and other input components.

In some examples, the eyewear device 100 includes a collection ofmotion-sensing components referred to as an inertial measurement unit472. The motion-sensing components may be micro-electro-mechanicalsystems (MEMS) with microscopic moving parts, often small enough to bepart of a microchip. The inertial measurement unit (IMU) 472 in someexample configurations includes an accelerometer, a gyroscope, and amagnetometer. The accelerometer senses the linear acceleration of thedevice 100 (including the acceleration due to gravity) relative to threeorthogonal axes (x, y, z). The gyroscope senses the angular velocity ofthe device 100 about three axes of rotation (pitch, roll, yaw).Together, the accelerometer and gyroscope can provide position,orientation, and motion data about the device relative to six axes (x,y, z, pitch, roll, yaw). The magnetometer, if present, senses theheading of the device 100 relative to magnetic north. The position ofthe device 100 may be determined by location sensors, such as a GPS unit473, one or more transceivers to generate relative position coordinates,altitude sensors or barometers, and other orientation sensors. Suchpositioning system coordinates can also be received over the wirelessconnections 425, 437 from the mobile device 401 via the low-powerwireless circuitry 424 or the high-speed wireless circuitry 436.

The IMU 472 may include or cooperate with a digital motion processor orprogramming that gathers the raw data from the components and compute anumber of useful values about the position, orientation, and motion ofthe device 100. For example, the acceleration data gathered from theaccelerometer can be integrated to obtain the velocity relative to eachaxis (x, y, z); and integrated again to obtain the position of thedevice 100 (in linear coordinates, x, y, and z). The angular velocitydata from the gyroscope can be integrated to obtain the position of thedevice 100 (in spherical coordinates). The programming for computingthese useful values may be stored in memory 434 and executed by thehigh-speed processor 432 of the eyewear device 100.

The eyewear device 100 may optionally include additional peripheralsensors, such as biometric sensors, specialty sensors, or displayelements integrated with eyewear device 100. For example, peripheraldevice elements may include any I/O components including outputcomponents, motion components, position components, or any other suchelements described herein. For example, the biometric sensors mayinclude components to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), tomeasure bio signals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), or to identify a person (e.g.,identification based on voice, retina, facial characteristics,fingerprints, or electrical bio signals such as electroencephalogramdata), and the like.

The mobile device 401 may be a smartphone, tablet, laptop computer,access point, or any other such device capable of connecting witheyewear device 100 using both a low-power wireless connection 425 and ahigh-speed wireless connection 437. Mobile device 401 is connected toserver system 498 and network 495. The network 495 may include anycombination of wired and wireless connections.

The context-sensitive remote control system 400, as shown in FIG. 4 ,includes a computing device, such as mobile device 401, coupled to aneyewear device 100 over a network. The context-sensitive remote controlsystem 400 includes a memory for storing instructions and a processorfor executing the instructions. Execution of the instructions of thecontext-sensitive remote control system 400 by the processor 432configures the eyewear device 100 to cooperate with the mobile device401. The context-sensitive remote control system 400 may utilize thememory 434 of the eyewear device 100 or the memory elements 540A, 540B,540C of the mobile device 401 (FIG. 5 ). Also, the context-sensitiveremote control system 400 may utilize the processor elements 432, 422 ofthe eyewear device 100 or the central processing unit (CPU) 530 of themobile device 401 (FIG. 5 ). In addition, the context-sensitive remotecontrol system 400 may further utilize the memory and processor elementsof the server system 498. In this aspect, the memory and processingfunctions of the context-sensitive remote control system 400 can beshared or distributed across the eyewear device 100, the mobile device401, and the server system 498.

The memory 434 includes, for execution by the processor 432, an activitydetection utility 462, a remote communication utility 464, a networkdetermination utility 466, and a debug utility 468. The activitydetection utility 462 monitors the high speed circuitry 430 and thelow-power circuitry 420 to determine the activity (e.g., email,painting, user-interface navigation, gaming, etc.) currently beingperformed by the eyewear device 100 that a user is interacting with. Inone example, the activity detection utility 462 identifies an activitypresenting controls or a graphical user interface (GUI) in theforeground of an image display 180. The remote communication utility 464identifies and establishes communication with a context-sensitive remotecontrol (e.g., mobile device 401). The network determination utility 466monitors available communication methods (e.g., Bluetooth LE and WiFi)and the bandwidth requirements for data flow between the electronicdevice and the context-sensitive remote control, and selects thecommunication method that utilizes the communication method able toprovide suitable communication with the lowest level of energyconsumption. The debug utility 468 detects when the electronic device isin a debug mode and sends debugging information to the context-sensitiveremote controller for display.

FIG. 5 is a high-level functional block diagram of an example mobiledevice 401. Mobile device 401 includes a flash memory 540A which storesprogramming to be executed by the CPU 530 to perform all or a subset ofthe functions described herein.

The mobile device 401 may include a camera 570 that comprises at leasttwo visible-light cameras (first and second visible-light cameras withoverlapping fields of view) or at least one visible-light camera and adepth sensor with substantially overlapping fields of view. Flash memory540A may further include multiple images or video, which are generatedvia the camera 570.

As shown, the mobile device 401 includes an image display 580, an imagedisplay driver 582 to control the image display 580, and a displaycontroller 584. In the example of FIG. 5 , the image display 580includes a user input layer 591 (e.g., a touchscreen) that is layered ontop of or otherwise integrated into the screen used by the image display580. The image display driver 582 is coupled to CPU 530 in order todrive the display 580.

Examples of touchscreen-type mobile devices that may be used include(but are not limited to) a smart phone, a personal digital assistant(PDA), a tablet computer, a laptop computer, or other portable device.However, the structure and operation of the touchscreen-type devices isprovided by way of example; the subject technology as described hereinis not intended to be limited thereto. For purposes of this discussion,FIG. 5 therefore provides a block diagram illustration of the examplemobile device 401 with a user interface that includes a touchscreeninput layer 891 for receiving input (by touch, multi-touch, or gesture,and the like, by hand, stylus or other tool) and an image display 580for displaying content

As shown in FIG. 5 , the mobile device 401 includes at least one digitaltransceiver (XCVR) 510, shown as WWAN XCVRs, for digital wirelesscommunications via a wide-area wireless mobile communication network.The mobile device 401 also includes additional digital or analogtransceivers, such as short-range transceivers (XCVRs) 520 forshort-range network communication, such as via NFC, VLC, DECT, ZigBee,Bluetooth™, or Wi-Fi. For example, short range XCVRs 520 may take theform of any available two-way wireless local area network (WLAN)transceiver of a type that is compatible with one or more standardprotocols of communication implemented in wireless local area networks,such as one of the Wi-Fi standards under IEEE 802.11.

To generate location coordinates for positioning of the mobile device401, the mobile device 401 can include a global positioning system (GPS)receiver. Alternatively, or additionally the mobile device 401 canutilize either or both the short range XCVRs 520 and WWAN XCVRs 510 forgenerating location coordinates for positioning. For example, cellularnetwork, Wi-Fi, or Bluetooth™ based positioning systems can generatevery accurate location coordinates, particularly when used incombination. Such location coordinates can be transmitted to the eyeweardevice over one or more network connections via XCVRs 510, 520.

The transceivers 510, 520 (i.e., the network communication interface)conforms to one or more of the various digital wireless communicationstandards utilized by modern mobile networks. Examples of WWANtransceivers 510 include (but are not limited to) transceiversconfigured to operate in accordance with Code Division Multiple Access(CDMA) and 3rd Generation Partnership Project (3GPP) networktechnologies including, for example and without limitation, 3GPP type 2(or 3GPP2) and LTE, at times referred to as “4G.” For example, thetransceivers 510, 520 provide two-way wireless communication ofinformation including digitized audio signals, still image and videosignals, web page information for display as well as web-related inputs,and various types of mobile message communications to/from the mobiledevice 401.

The mobile device 401 further includes a microprocessor that functionsas a central processing unit (CPU); shown as CPU 530 in FIG. 5 . Aprocessor is a circuit having elements structured and arranged toperform one or more processing functions, typically various dataprocessing functions. Although discrete logic components could be used,the examples utilize components forming a programmable CPU. Amicroprocessor for example includes one or more integrated circuit (IC)chips incorporating the electronic elements to perform the functions ofthe CPU. The CPU 530, for example, may be based on any known oravailable microprocessor architecture, such as a Reduced Instruction SetComputing (RISC) using an ARM architecture, as commonly used today inmobile devices and other portable electronic devices. Of course, otherarrangements of processor circuitry may be used to form the CPU 530 orprocessor hardware in smartphone, laptop computer, and tablet.

The CPU 530 serves as a programmable host controller for the mobiledevice 401 by configuring the mobile device 401 to perform variousoperations, for example, in accordance with instructions or programmingexecutable by CPU 530. Example operations include various generaloperations of the mobile device, as well as operations related to theprogramming for applications on the mobile device.

The mobile device 401 includes a memory or storage system, for storingprogramming and data. In the example, the memory system may include aflash memory 540A, a random-access memory (RAM) 540B, and other memorycomponents 540C, as needed. The RAM 540B serves as short-term storagefor instructions and data being handled by the CPU 530, e.g., as aworking data processing memory. The flash memory 540A typically provideslonger-term storage.

In the example of mobile device 401, the flash memory 540A is used tostore programming or instructions for execution by the CPU 530.Depending on the type of device, the mobile device 401 stores and runs amobile operating system through which specific applications areexecuted. Examples of mobile operating systems include Google Android,Apple iOS (for iPhone or iPad devices), Windows Mobile, Amazon Fire OS,RIM BlackBerry OS, or the like.

The memory 540A includes layout configurations 560 (see, for example,layout configurations depicted in FIGS. 7A, 8A, and 9A) for display onthe context-sensitive remote control to control activity on theelectronic device (e.g., eyewear device 100). In one example,identifiers for the layout configurations and corresponding layoutconfiguration memory locations are stored in a table in flash memory540A.

Additionally, the memory 540A includes, for execution by the processor530, an activity detection utility 562, a remote communication utility564, a network determination utility 566, an orientation detectionutility 568, and a touch detection utility 569.

The activity detection utility 562 monitors communications from theelectronic device and detects the activity currently being performed onthe electronic device from the monitored communications. The remotecommunication utility 564, e.g., in conjunction with the remotecommunication utility 464, identifies and establishes communication withthe electronic device. The network determination utility 566, e.g., inconjunction with the network determination utility 466, monitorsavailable communication methods (e.g., Bluetooth LE and WiFi) and thenecessary bandwidth for data flow between the mobile device and thecontext-sensitive remote control, and selects the communication methodthat utilizes the communication method able to provide suitablecommunication with the lowest level of energy consumption. Theorientation detection utility 568 detects whether the context-sensitiveremote control is in a horizontal orientation or a vertical orientation(e.g., based on input from IMU 572). The touch detection utilitymonitors finger presses (e.g., location and duration) on the display 580(e.g., based on signals from user input layer 591).

FIG. 6 depicts an electronic device (eyewear device 100), acontext-sensitive remote control (mobile device 401), and a networkdevice 601. The eyewear device 100 may communicate directly with themobile device 401 (e.g., via a Bluetooth™ connection) or indirectly viaa wireless network device 601. In one example, the eyewear device 100and the mobile device 401 initially establish a direct Bluetoothconnection. If the eyewear device 100 or the mobile device 401 determinethat a WiFi connection is available and that bandwidth requirementsexceed that available via Bluetooth, the eyewear device 100 and themobile device 401 may transition to communicating via WiFi. Otherwise,the eyewear device 100 and the mobile device 401 may continue using thedirect Bluetooth connection, which has lower power consumption and lessbandwidth than WiFi.

FIG. 7A is an illustration of a context-sensitive remote control with acontroller layout configuration. The illustrated controller layoutconfiguration includes a first joystick type 702A (FIG. 7B) in a firstboundary box 703A, a second joystick type 702B (FIG. 7C) in a secondboundary box 703B, a first configurable button 704A, and a secondconfigurable button 704B. The joystick types may include additionaltypes of joysticks such as a third joystick type 702C (FIG. 7D).

The illustrated controller layout configuration (and other configurationlayouts) also includes a controller layout shortcut button 706A, akeyboard layout shortcut button 706B, and a touchpad layout shortcutbutton 706C. In one example, the shortcut buttons may be displayedduring set-up of the context-sensitive remote controller, and thereafteromitted. In another example, the shortcut buttons remain available toenable a user to override a particular layout configuration. In anotherexample, the shortcut buttons are available in one orientation (e.g., ahorizontal orientation; see FIG. 9B), but not another (e.g., a verticalorientation; see FIG. 9A)

FIGS. 8A and 8B are illustrations of a context-sensitive remote controlwith a touchpad layout configuration in a vertical orientation (FIG. 8A)and a horizontal orientation (FIG. 8B), respectively. The illustratedvertical touchpad layout configuration includes a vertical touchpadinput area that covers at least substantially all (i.e., greater than90%) of the mobile device display area. The illustrated horizontaltouchpad layout configuration includes a horizontal touchpad input areathat also covers at least substantially all (i.e., greater than 90%) ofthe mobile device display area.

FIGS. 9A and 9B are illustrations of a context-sensitive remote controlwith a keyboard layout configuration in a vertical orientation (FIG. 9A)and a horizontal orientation (FIG. 9B), respectively. The illustratedvertical controller layout configuration includes a keypad 902A coveringapproximately half (i.e., 40% to 60%) of the mobile device display areaand a touchpad input area 904 covering the remaining portion (i.e., 60%to 40%) of the mobile device display area. The illustrated horizontalcontroller layout configuration includes a larger keypad 902B than thekeypad 902A in vertical controller layout, but no touchpad.

FIGS. 10A-10G are a flow charts 1000, 1010, 1012-1, 1012-2, 1014, 1016,and 1030 listing steps in example methods for implementing acontext-sensitive remote control. Although the steps are described withreference to the eyewear device 100 as the electronic device beingcontrolled and the mobile device 401 as the context-sensitive remotecontrol controlling the electronic device, other implementations of thesteps described, for other types of electronic devices, will beunderstood by one of skill in the art from the description herein.Additionally, it is contemplated that one or more of the steps shown inFIGS. 10A-10G, and described herein, may be omitted, performedsimultaneously or in a series, performed in an order other thanillustrated and described, or performed in conjunction with additionalsteps.

FIG. 10A depicts a flow chart 1000 for configuring a context-sensitiveremote control (e.g., mobile device 401). At block 1010, thecontext-sensitive remote control establishes communication with anelectronic device (e.g., eyewear device 100). The context-sensitiveremote control establishes communication with the electronic device viarespective transceivers 424/520.

In an example, processor 432 executes remote communication utility 464and processor 530 executes remote communication utility 564 to exchangeinformation for initiating communication there between (block 1010A;FIG. 10B). The context-sensitive remote control and electronic devicemay initiate communication using a direct communication link (e.g.,Bluetooth LE). Thereafter, the context-sensitive remote control and theelectronic device each monitor available wireless networks (e.g., WiFiby periodically requesting signal strength information from theirrespective WiFi transceivers) and share identification information ofthe available wireless networks to which they have access (block 1010B).The context-sensitive remote control and the electronic deviceadditionally monitor communication requirements (e.g., bandwidth)necessary to enable all the features of the context-sensitive remotecontrol (block 1010C). For example, control information that enables thecontext-sensitive remote control to input text on the electronic devicerequires relatively low amount of bandwidth that can be adequatelytransferred via Bluetooth LE. Streaming video from the electronic devicefor display on the context-sensitive remote control (e.g., for debuggingan application on the electronic device) may require greater amounts ofbandwidth (such as available via a WiFi connection) for acceptableperformance.

The context-sensitive remote control selects the communication methodresponsive to the wireless networks available to both thecontext-sensitive remote control and the electronic device and thecommunication requirements (block 1010D). For example, if thecontext-sensitive remote control determines that a particular WiFiconnection is available to both the context-sensitive remote control andthe electronic device (e.g., based on information collected from itsWiFi transceiver and WiFi identification information shared by theelectronic device; block 1010B), and that bandwidth requirements exceedthat available via Bluetooth, the context-sensitive remote control maytransition to communicating with the electronic device via WiFi (e.g.,by sending a request to the electronic device and switching thecommunication method upon receiving a positive response). Otherwise, thecontext-sensitive remote control and electronic device may continueusing the direct Bluetooth connection, which has lower power consumptionand less bandwidth than WiFi. Once a communication method is selected,processor 432 and processor 530 route communications throughtransceivers for the selected communication method (block 1010E).

Referring back to FIG. 10A, at block 1012, the context-sensitive remotecontrol detects an activity being performed by the electronic device(e.g., email, painting, user-interface navigation, gaming, etc.). In anexample, processor 432 executes activity detection utility 462 andprocessor 530 executes activity detection utility 562 to enablecontext-sensitive remote control to detect the activity being performedon the electronic device.

The electronic device performs the steps of flow chart 1012-1 to detectactivity of the electronic device and the context-sensitive remotecontrol performs the steps of flow chart 1012-2 to detect activity ofthe electronic device. At block 1012A, the electronic device detects acurrent activity being performed by an electronic device. In an example,the processor 432 for the eyewear device, executing activity detectionutility 462, monitors the threads it is currently executing. Eachactivity can have multiple threads of execution, and each thread cancreate windows. The thread that creates the window with which the useris currently working is referred to as a foreground thread, and theassociated window is called the foreground window. The processoridentifies the activity associated with the foreground window (bydetecting the current foreground thread and identifying the associatedactivity) as the current activity.

At block 1012B, the processor 432 selects an activity indicatorassociated with the selected activity. For example, the processor mayselect a “1” for gaming, a “2” for touchpad input, a “3” foruser-interface navigation, and a “4” for text/keyboard input). Theprocessor 432 stores the selected indicator in memory 434.

At block 1012C, the processor 432 of the electronic device sends theindicator to the context sensitive remote control. The processor 432retrieves the indicator from the memory 434 and sends a communicationincluding the indicator to the context-sensitive remote control via theestablished communication channel (block 1010), e.g., via transceiver424 or transceiver 436.

At block 1012D, the processor 530 of the context-sensitive remotecontrol receives the indicator. The processor 530 receives the indicatorfrom the context-sensitive remote control via the establishedcommunication channel, e.g., via transceiver 520 or transceiver 510. Theprocessor 530 stores the received indicator in memory 540.

At block 1012E, the processor 530 of the context-sensitive remotecontrol determines the activity being performed by the electronic deviceresponsive the received indicator. The processor 530 may determine theactivity by retrieving the activity associated with the receivedindicator (block 1012D) from a look-up table in memory 540. The look-uptable may include a list of indicators and associated activities. Forexample, the look-up table may include a “1” associated with gaming, a“2” associated with touchpad input, a “3” associated with user-interfacenavigation, and a “4” associated with text/keyboard input).

Referring back to FIG. 10A, at block 1014, the context-sensitive remotecontrol selects the controller layout configuration responsive to theactivity being performed on the electronic device. In an example, theprocessor 530 selects the controller layout by implementing the steps inflow chart 1014 (FIG. 10E).

At block 1014A, the processor 530 determines the controller layoutconfiguration (e.g., controller, keyboard, touchpad, etc.) In anexample, the processor 530 determines the controller layoutconfiguration by retrieving the controller layout configurationassociated with the determined activity (e.g., which is based on thereceived indicator) from a look-up table in memory 540. The look-uptable may include a list of activities and associated controller layoutconfigurations.

Additionally, at block 1014B, the processor 530 may detect controllerorientation (horizontal or vertical). In an example, the processor 530detects orientation by querying the IMU 572. At decisions block 1014C,if the controller is determined to be horizontal, processing proceeds atblock 1014D with selection of a first layout of the determinedcontroller layout configuration (e.g., as shown in FIGS. 7A, 8B, and9B). Otherwise, processing proceeds at block 1014E with selection of asecond layout of the determined controller layout configuration (e.g.,as shown in FIGS. 8A and 9A).

Referring back to FIG. 10A, at block 1016, the context-sensitive remotecontrol adjusts the controller layout. For example, thecontext-sensitive remote control may adjust the controller layout byadjusting the joysticks. In accordance with this example, at block1016A, the processor 530 adjusts the controller layout by detecting afirst touch on the display 580 in a first boundary box 703A (e.g., viathe user input layer 591). At block 1016B, the processor 530 centers thefirst joystick 702A on the first touch within the first boundary box703A (e.g., via the driver 582). At block 1016C, the processor 530adjusts the controller layout by detecting a second touch on the display580 in a second boundary box 703B (e.g., via the user input layer 591).At block 1016D, the processor 530 centers the second joystick 702B onthe second touch within the second boundary box 703B (e.g., via thedriver 582).

Referring back to FIG. 10A, at block 1018, the context-sensitive remotecontrol presents the controller layout configuration. The processor 530may retrieve the controller layout configuration from memory 540 andpresent it on display 580 via driver 582.

FIG. 10G depicts a flow chart 1030 of steps for overriding thecontroller layout configuration. At block 1032, the context-sensitiveremote control detects a user selection of a layout configuration. In anexample, the processor 530 monitors screen presses on the user inputlayer 591 of the display 580 for touches corresponding toreconfiguration buttons on the display 580. Each button corresponds to acontroller layout configuration stored in memory 540A

At block 1034, the context-sensitive remote control identifies acontroller layout configuration based on the user selection. In anexample, the processor 530 identifies a controller layout configurationresponsive to the user selection. The processor 530 may identify thecontroller layout configuration corresponding to the particularreconfiguration button selected by the user, e.g., by retrieving from atable stored in memory 540.

At block 1036, the context-sensitive remote control replaces theactivity-based controller layout configuration with the userselection-based controller layout configuration. In an example, theprocessor 530 replaces the controller layout selected according to theprocess of FIG. 10A with the controller layout configuration based onthe user selection in block 1032. The processor 530 may retrieve theuser-selection based controller layout configuration from memory 540 andpresent it on display 580 via driver 582.

Any of the functionality described herein for an electronic device(e.g., the eyewear device 100), a context-sensitive remote control(e.g., the mobile device 401), and the server system 498 can be embodiedin one or more computer software applications or sets of programminginstructions, as described herein. According to some examples,“function,” “functions,” “application,” “applications,” “instruction,”“instructions,” or “programming” are program(s) that execute functionsdefined in the programs. Various programming languages can be employedto develop one or more of the applications, structured in a variety ofmanners, such as object-oriented programming languages (e.g.,Objective-C, Java, or C++) or procedural programming languages (e.g., Cor assembly language). In a specific example, a third-party application(e.g., an application developed using the ANDROID™ or IOS™ softwaredevelopment kit (SDK) by an entity other than the vendor of theparticular platform) may include mobile software running on a mobileoperating system such as IOS™, ANDROID™, WINDOWS® Phone, or anothermobile operating systems. In this example, the third-party applicationcan invoke API calls provided by the operating system to facilitatefunctionality described herein.

Hence, a machine-readable medium may take many forms of tangible storagemedium. Non-volatile storage media include, for example, optical ormagnetic disks, such as any of the storage devices in any computerdevices or the like, such as may be used to implement the client device,media gateway, transcoder, etc. shown in the drawings. Volatile storagemedia include dynamic memory, such as main memory of such a computerplatform. Tangible transmission media include coaxial cables; copperwire and fiber optics, including the wires that comprise a bus within acomputer system. Carrier-wave transmission media may take the form ofelectric or electromagnetic signals, or acoustic or light waves such asthose generated during radio frequency (RF) and infrared (IR) datacommunications. Common forms of computer-readable media thereforeinclude for example: a floppy disk, a flexible disk, hard disk, magnetictape, any other magnetic medium, a CD-ROM, DVD or DVD-ROM, any otheroptical medium, punch cards paper tape, any other physical storagemedium with patterns of holes, a RAM, a PROM and EPROM, a FLASH-EPROM,any other memory chip or cartridge, a carrier wave transporting data orinstructions, cables or links transporting such a carrier wave, or anyother medium from which a computer may read programming code or data.Many of these forms of computer readable media may be involved incarrying one or more sequences of one or more instructions to aprocessor for execution.

Except as stated immediately above, nothing that has been stated orillustrated is intended or should be interpreted to cause a dedicationof any component, step, feature, object, benefit, advantage, orequivalent to the public, regardless of whether it is or is not recitedin the claims.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”“includes,” “including,” or any other variation thereof, are intended tocover a non-exclusive inclusion, such that a process, method, article,or apparatus that comprises or includes a list of elements or steps doesnot include only those elements or steps but may include other elementsor steps not expressly listed or inherent to such process, method,article, or apparatus. An element preceded by “a” or “an” does not,without further constraints, preclude the existence of additionalidentical elements in the process, method, article, or apparatus thatcomprises the element.

Unless otherwise stated, any and all measurements, values, ratings,positions, magnitudes, sizes, and other specifications that are setforth in this specification, including in the claims that follow, areapproximate, not exact. Such amounts are intended to have a reasonablerange that is consistent with the functions to which they relate andwith what is customary in the art to which they pertain. For example,unless expressly stated otherwise, a parameter value or the like mayvary by as much as plus or minus ten percent from the stated amount orrange.

In addition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in various examples for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimed examplesrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, the subject matter to be protected liesin less than all features of any single disclosed example. Thus, thefollowing claims are hereby incorporated into the Detailed Description,with each claim standing on its own as a separately claimed subjectmatter.

While the foregoing has described what are considered to be the bestmode and other examples, it is understood that various modifications maybe made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that they may be appliedin numerous applications, only some of which have been described herein.It is intended by the following claims to claim any and allmodifications and variations that fall within the true scope of thepresent concepts.

What is claimed is:
 1. A context-sensitive remote control for use withan electronic device, the electronic device configured to perform aplurality of activities, the context-sensitive remote controlcomprising: a display having a display area; at least one transceiver; amemory storing a plurality of controller layout configurations forpresentation in the display area, each of the plurality of controllerlayout configurations including at least one controller reconfigurationbutton and each of the controller reconfiguration buttons associatedwith a respective one of the plurality of controller layoutconfigurations; a processor coupled to the at least one transceiver andthe memory; and programming in the memory, wherein execution of theprogramming by the processor configures the processor to performfunctions, including functions to: establish, via the at least onetransceiver, communication with the electronic device; detect one of theplurality of activities currently being performed by the electronicdevice; select one of the plurality of controller layout configurationsresponsive to the detected one of the plurality of activities currentlybeing performed by the electronic device; present, via the display, theselected one of the plurality of controller layout configurations in thedisplay area of the display; detect a user selection of one of theplurality of controller reconfiguration buttons in the display area; andreplace, via the display, the selected one of the plurality ofcontroller layout configurations with the respective one of theplurality of controller layout configurations associated with thedetected user selection in the display area of the display.
 2. Thecontext-sensitive remote control of claim 1, wherein the plurality ofcontroller layout configurations comprises a game controllerconfiguration, a keyboard configuration, and a touchpad configuration.3. The context-sensitive remote control of claim 2, wherein theplurality of controller layout configurations further comprises a debugconfiguration.
 4. The context-sensitive remote control of claim 1,wherein the plurality of controller layout configurations comprises atleast one of a game controller configuration, a keyboard configuration,or a touchpad configuration comprising a first layout for the displayarea of the display and a second layout for the display area of thedisplay and wherein the context-sensitive remote control furthercomprises: an inertial measurement unit (IMU) coupled to the processor,the IMU configured to detect at least one of orientation or movement ofthe context-sensitive remote control; wherein the execution of theprogramming by the processor configures the context-sensitive remotecontrol to perform additional functions, including functions to: detect,using the IMU, if the context sensitive remote is in a first orientationor a second orientation; wherein the select function is configured to:select the first layout when the context-sensitive remote is in thefirst orientation; and select the second layout when thecontext-sensitive remote is in the second orientation.
 5. Thecontext-sensitive remote control of claim 4, wherein the firstorientation is a horizontal orientation, the second orientation is avertical orientation, the first layout of the keyboard configurationincludes a first keyboard covering at least 90% of the display area, andthe second layout of the keyboard configuration includes a secondkeyboard covering a first portion of the display area and a touchpadentry region covering a second portion of the display area.
 6. Thecontext-sensitive remote control of claim 1, wherein the display area istouch sensitive and includes a first boundary box and a second boundarybox, the plurality of controller layout configurations comprises a gamecontroller configuration including a first a joystick and a secondjoystick, and the execution of the programming by the processorconfigures the context-sensitive remote control to perform additionalfunctions, including functions to; detect a first initial touch at afirst initial location within the first boundary box; detect a secondinitial touch at a second initial location within the second boundarybox; and configure the game controller configuration with the firstjoystick centered at the first initial location within the firstboundary box and the second joystick centered at the second initiallocation within the second boundary box.
 7. The context-sensitive remotecontrol of claim 1, wherein the display area is touch sensitive.
 8. Thecontext-sensitive remote control of claim 1, wherein the at least onetransceiver comprises; a first transceiver; and a second transceiver;wherein the execution of the programming by the processor configures thecontext-sensitive remote control to perform additional functions,including functions to: monitor availability of wireless networks;monitor communication requirement between the context-sensitive remotecontrol and the electronic device; and select the first transceiver orthe second transceiver for communication between the context-sensitiveremote control and the electronic device responsive to the availabilityof the wireless networks and the communication requirements.
 9. Acontext-sensitive remote control method for use with an electronicdevice, the electronic device configured to perform a plurality ofactivities, the method comprising: establishing, by a context sensitiveremote control, communication with the electronic device, thecontext-sensitive remote control comprising at least one transceiver anda display having a display area; detecting one of the plurality ofactivities currently being performed by the electronic device; selectingone of a plurality of controller layout configurations responsive to thedetected one of the plurality of activities currently being performed bythe electronic device, each of the plurality of controller layoutconfigurations including at least one controller reconfiguration buttonand each of the controller reconfiguration buttons associated with arespective one of the plurality of controller layout configurations;presenting, via the display, the selected one of the plurality ofcontroller layout configurations in the display area of the display;detecting a user selection of one of the plurality of controllerreconfiguration buttons in the display area; and replacing, via thedisplay, the selected one of the plurality of controller layoutconfigurations with the respective one of the plurality of controllerlayout configurations associated with the detected user selection in thedisplay area of the display.
 10. The method of claim 9, wherein theplurality of controller layout configurations comprises a gamecontroller configuration, a keyboard configuration, and a touchpadconfiguration.
 11. The method of claim 10, wherein the plurality ofcontroller layout configurations further comprises a debugconfiguration.
 12. The method of claim 9, wherein the plurality ofcontroller layout configurations comprises at least one of a gamecontroller configuration, a keyboard configuration, or a touchpadconfiguration comprising a first layout for the display area of thedisplay and a second layout for the display area of the display andwherein the method further comprises: detecting, using an inertialmeasurement unit (IMU), if the context sensitive remote is in a firstorientation or a second orientation; wherein the selecting comprises:selecting the first layout when the context-sensitive remote is in thefirst orientation; and selecting the second layout when thecontext-sensitive remote is in the second orientation.
 13. The method ofclaim 12, wherein the first orientation is a horizontal orientation, thesecond orientation is a vertical orientation, the first layout of thekeyboard configuration includes a first keyboard covering at least 90%of the display area, and the second layout of the keyboard configurationincludes a second keyboard covering a first portion of the display areaand a touchpad entry region covering a second portion of the displayarea.
 14. The method of claim 9, wherein the display area is touchsensitive and includes a first boundary box and a second boundary box,the plurality of controller layout configurations comprises a gamecontroller configuration including a first a joystick and a secondjoystick, and the method further comprises: detecting a first initialtouch at a first initial location within the first boundary box;detecting a second initial touch at a second initial location within thesecond boundary box; and configuring the game controller configurationwith the first joystick centered at the first initial location withinthe first boundary box and the second joystick centered at the secondinitial location within the second boundary box.
 15. The method of claim9, wherein the at least one transceiver comprises a first transceiverand a second transceiver, the method further comprising; monitoringavailability of wireless networks; monitoring communication requirementbetween the context-sensitive remote control and the electronic device;and selecting the first transceiver or the second transceiver forcommunication between the context-sensitive remote control and theelectronic device responsive to the availability of the wirelessnetworks and the communication requirements.
 16. A non-transitorycomputer-readable medium storing program code which, when executed, isoperative to cause an electronic processor to perform the steps of:establishing, by a context sensitive remote control, communication withan electronic device configured to perform a plurality of activities,the context-sensitive remote control comprising at least one transceiverand a display having a display area; detecting one of the plurality ofactivities currently being performed by the electronic device; selectingone of a plurality of controller layout configurations responsive to thedetected one of the plurality of activities currently being performed bythe electronic device, each of the plurality of controller layoutconfigurations including at least one controller reconfiguration buttonand each of the controller reconfiguration buttons associated with arespective one of the plurality of controller layout configurations;detecting a user selection of one of the plurality of controllerreconfiguration buttons in the display area; and presenting, via thedisplay, the selected one of the plurality of controller layoutconfigurations in the display area of the display.
 17. Thenon-transitory computer-readable medium storing program code of claim16, wherein the plurality of controller layout configurations comprisesat least one of a game controller configuration, a keyboardconfiguration, or a touchpad configuration comprising a first layout forthe display area of the display and a second layout for the display areaof the display and wherein the program code, when executed, is operativeto cause the electronic processor to perform the steps of: detecting,using an inertial measurement unit (IMU), if the context sensitiveremote is in a first orientation or a second orientation; wherein theselecting comprises: selecting the first layout when thecontext-sensitive remote is in the first orientation; and selecting thesecond layout when the context-sensitive remote is in the secondorientation.
 18. The non-transitory computer-readable medium storingprogram code of claim 17, wherein the first orientation is a horizontalorientation, the second orientation is a vertical orientation, the firstlayout of the keyboard configuration includes a first keyboard coveringat least 90% of the display area, and the second layout of the keyboardconfiguration includes a second keyboard covering a first portion of thedisplay area and a touchpad entry region covering a second portion ofthe display area.
 19. The non-transitory computer-readable mediumstoring program code of claim 16, wherein the at least one transceivercomprises a first transceiver and a second transceiver and wherein theprogram code, when executed, is operative to cause the electronicprocessor to perform the steps of: monitoring availability of wirelessnetworks; monitoring communication requirement between thecontext-sensitive remote control and the electronic device; andselecting the first transceiver or the second transceiver forcommunication between the context-sensitive remote control and theelectronic device responsive to the availability of the wirelessnetworks and the communication requirements.
 20. The non-transitorycomputer-readable medium storing program code of claim 16, wherein thedisplay area is touch sensitive and includes a first boundary box and asecond boundary box, the plurality of controller layout configurationscomprises a game controller configuration including a first a joystickand a second joystick, and wherein the program code, when executed, isoperative to cause the electronic processor to perform the steps of:detecting a first initial touch at a first initial location within thefirst boundary box; detecting a second initial touch at a second initiallocation within the second boundary box; and configuring the gamecontroller configuration with the first joystick centered at the firstinitial location within the first boundary box and the second joystickcentered at the second initial location within the second boundary box.